Systems and Methods of Profiling Data For Integration

ABSTRACT

The present invention is generally directed to systems and methods for gathering information about nonnative data, comparing nonnative data elements to information defining nonnative data, comparing native data elements to information defining native data, establishing transformation rules, and integrating the nonnative and native data.

FIELD OF THE INVENTION

To present invention generally relates to systems and methods for profiling native and nonnative data for integration.

BACKGROUND

Data profiling can provide extremely useful information about the underlying data. For example, data profiling can be used to: discover the quality, characteristics, and potential problems of data; catalog and analyze metadata and discover metadata relationships; and help understand and prepare data for integration. The profiling process typically includes collecting information, such as statistics (e.g., mean and median values) and values (e.g., maximum and minimum values), of the underlying data. In the past, data profiling was performed manually. That is, to profile data, data analysts typically “eye balled” the data and collected statistics and other information about the data as they reviewed it. Manually analyzing data is an extremely time-consuming and error-prone process. Thus, given the amount of data used by businesses today, the manual method of profiling quickly became impractical. In response to the need for more efficient means of data profiling, various vendors began to develop and commercialize data profiling applications and tools. For example, IBM® and Computer Associates® sell a variety of tools, such as software applications, that can be implemented to profile data. However, the tools and methods currently available do not provide a well-refined solution for profiling data for integration.

Merging businesses, streamlining departments, parent companies operating subsidiary entities, and the like have given rise to a need to integrate data from a variety of sources. For example, over the years, United Parcel Service of America, Inc. (UPS®), has acquired various entities. When UPS® acquires entities such as the Overnite Corporation, it has a compelling interest in making use of the data of the acquired companies. What makes data integration challenging is the fact that while two data sources may comprise similar data, the data sources likely reference, store, and interact with the data differently. Thus, integrating data from unique data sources has posed a challenge to data integration efforts. Therefore, a need exists for systems and methods that aid in efficiently and effectively gathering, comparing, documenting, creating, and storing information about the data being profiled for potential integration opportunities, and for actually integrating the data.

BRIEF SUMMARY

In general, embodiments of the present invention provide for systems and methods that aid in efficiently and effectively gathering, comparing, documenting, creating, storing information about data being profiled for potential integration opportunities and for actually integrating the data.

In accordance with one aspect, a method is provided for integrating nonnative data with native data. In one embodiment, the method may include: (1) receiving information defining normative data; (2) expanding the nonnative data element tokens; (3) searching native data to determine if information associated with any of the respective native data elements and information associated with any of the respective full nonnative data element names are similar; (4) importing the normative data; (5) identifying values of the nonnative data; (6) comparing the normative data to the information defining the normative data to determine if there are any discrepancies between the information defining the normative data and the normative data; (7) recording the discrepancies and determining if the information defining the normative data needs to be modified; (8) if necessary, modifying the information defining the normative data; (9) in response to a search determining that at least one native data element and one full nonnative data element name are associated with a similar type of information, receiving information defining the similar native data elements; (10) comparing the normative data to the information defining the similar native data elements to determine if there are discrepancies; (11) recording the discrepancies and determining if the information defining the native data needs to be modified; and (12) if necessary, modifying the information defining the similar native data elements.

In accordance with another aspect, a system is provided for integrating normative data with native data. In one embodiment, the system may include a processor configured to: (1) receive information about native data and normative data, including full normative data element names and native data elements; (2) search native data to determine if information associated with any of the respective native data elements and information associated with any of the respective full normative data element names are similar; (3) import the normative data; (4) identify values of the normative data; (5) record any discrepancies between the information defining the nonnative data and the nonnative data; (5) receive information defining the similar native data elements; and (6) record any discrepancies between the nonnative data to the information defining the similar native data elements.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 shows an exemplary embodiment of a data profiling system.

FIG. 2 shows an exemplary embodiment of steps for profiling data.

FIG. 3 shows an exemplary embodiment of a way to access information defining data.

FIG. 4 shows exemplary data element tokens and their expanded data element names.

FIGS. 5-11 show exemplary steps and outputs of a name matcher module in an exemplary embodiment.

FIGS. 12 and 13 show exemplary steps and outputs of a data analysis module in an exemplary embodiment.

FIG. 14 shows exemplary input for a data element matcher module in an exemplary embodiment.

FIGS. 15 and 16 show exemplary reports generated by the data element matcher module in an exemplary embodiment.

FIG. 17 shows an exemplary output of a data frequency module in an exemplary embodiment.

DETAILED DESCRIPTION OF THE INVENTION

The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to like elements throughout.

As should be appreciated, the exemplary embodiments may be implemented as methods, apparatus, network entities, systems, or computer program products. Accordingly, the exemplary embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the various implementations may take the form of a computer program product on a computer-readable storage medium having computer-readable program instructions (e.g., computer software) embodied in the storage medium. More particularly, implementations of the exemplary embodiments may take the form of web-implemented computer software. Any suitable computer-readable storage medium may be utilized including hard disks, CD-ROMs, optical storage devices, or magnetic storage devices.

The exemplary embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatus, network entities, systems, and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions, e.g., as logical steps. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus implement the functions specified in the flowchart block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including computer-readable instructions for implementing the functionality specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrations support various combinations for performing the specified functions, combinations of steps for performing the specified functions and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.

Exemplary Architecture

FIG. 1 shows a data profiling system 100 according to an exemplary embodiment. The phrase “data profiling system” is used generically to refer to any computer, mainframe, desktop, notebook or laptop, distributed system, network entity, gateway, router, server, hub, switch, repeater, or any other processing device configured to perform the functions described herein. As will be understood from FIG. 1, in this embodiment, the data profiling system 100 is connected to one or more networks (e.g., connected via a local area network (LAN), metropolitan area network (MAN), wide area network (WAN), the Internet, or private network) to communicate with other computing entities, including databases. This communication is typically executed using a wired data transmission protocol, such as X.25, ISDN, DSL, PIP, Ethernet, ATM, frame relay, DOCSIS, or any other wired transmission protocol. Similarly, the data profiling system 100 may be configured to communicate via wireless external communication networks using any of a variety of protocols. Also, the data profiling system 100 may be embodied in a distributed computing system. That is, the data profiling system 100 may be located remotely from any entity with which it communicates.

Alternatively, in another embodiment, the data profiling system 100 may reside on the same computer system as the entities with which it communicates via a network, system interface, or bus. In these embodiments, the data profiling system 100 may be located remotely from the databases it accesses or the systems with which it communicates. In yet another embodiment, the data profiling system 100 may implement the functionality described herein via modules, e.g., a name matcher module 170, a data conversion module 160, a data analysis module 150, a data element matcher module 140, and a data frequency module 130. As will be recognized, though, the architectures described herein are exemplary and not limiting to the various embodiments.

As mentioned, FIG. 1 shows one embodiment of the data profiling system 100 implementing the described functionality as modules. As will be understood from this figure, in this embodiment, the data profiling system 100 includes a processor 163 that communicates with other elements within the data profiling system 100 via a system interface or bus 161. The data profiling system 100 also includes a display/input device 164 for receiving and displaying data. This display/input device 164 may be, for example, a keyboard or pointing device used in combination with a monitor. The data profiling system 100 further includes memory 166, which may include both read only memory (ROM) 165 and random access memory (RAM) 167. The data profiling system's ROM 165 is used to store a basic input/output system 26 (BIOS), containing the basic routines that help to transfer information between elements within the data profiling system 100.

In addition, the data profiling system 100 may include a storage device 163, such as a hard disk drive, a floppy disk drive, a CD ROM drive, or an optical disk drive, for storing information on various computer-readable media, such as a hard disk, a removable magnetic disk, or a CD-ROM disk. As will be appreciated, each of these storage devices 163 may be connected to the system bus 161 by an appropriate interface. The storage devices 163 and their associated computer-readable media provide nonvolatile storage. The computer-readable media described above could be replaced by any other type of computer-readable media, e.g., magnetic cassettes, flash memory cards, digital video disks, and Bernoulli cartridges.

A number of program modules may be stored by the various storage devices and within RAM 167. Such program modules may include an operating system 180, a name matcher module 170, a data conversion module 160, a data analysis module 150, a data element matcher module 140, and a data frequency module 130. The name matcher module 170, data conversion module 160, data analysis module 150, data element matcher module 140, and data frequency module 130 control certain aspects of the operation of the data profiling system 100, with the assistance of the processor 163 and operating system 180. As discussed briefly, the modules implement various functions of the data profiling system 100; however, the modules are not necessarily integrated or standalone modules. Thus, in some embodiments, the output from one module might require manual input into another module.

Also located within the data profiling system 100 is a network interface 174 for interfacing and communicating with other elements of a computer network. It will be appreciated that one or more of the data profiling system 100 components may be located remotely from other data profiling system 100 components. Furthermore, one or more of the components may be combined, and additional components performing functions described herein may be included in the data profiling system 100.

Brief Overview

In general, the exemplary embodiments of the present invention provide methods, apparatus, network entities, systems, and computer program products for profiling native data and nonnative data for integration possibilities. The meaning of the terms “native data” and “nonnative data” are a matter of perspective. For example, native data can be data that is internal to a primary source. Thus, nonnative data can be data that is external to the primary source. A primary source (native data) could be a record, column, table, database, department, company, a subsidiary, or the like. For instance, over the years, UPS has acquired various entities, such as the Overnite Corporation (“Overnite”). When UPS acquires entities such as Overnite, it typically has an interest in making use of the data of the acquired entities (e.g., nonnative data). In such cases, the nonnative data (Overnite's data) can be profiled for possible integration with the native data (UPS' data). As indicated though, the terms native data and nonnative data are used generically and can be used to represent data from one or more data sources, such as data from different departments, companies, or related business entities.

A. Nonnative Information Gathering 1. Gather Information Defining Nonnative Data

In one embodiment, the first step in profiling data is to identify the data source(s) and/or the nonnative data. As indicated in Step 200 of FIG. 2, after identifying the data sources and the nonnative data, analysts can begin to gather, import, and/or receive information defining the nonnative data, e.g., metadata. The terms gather, import, and receive are used generically to indicate that the information is somehow collected (hereinafter the terms are used interchangeably). For example, as shown in FIG. 3, the terms include retrieving the information, such as by accessing files containing the specified information stored in a repository. In this step, only information defining the nonnative data is typically gathered, but information defining the native data could be gathered as well. Information defining the nonnative data can also be acquired later, such as by the data analysis module 150 in Step 225 (FIG. 2). As should be recognized, information defining the native data can also be gathered if desired. Moreover, the type of information gathered can vary. For instance, in one embodiment, the information defining the data may include data dictionaries, metadata (tool-generated or home-grown), copybooks, table schemas, data models, common tables and contents, requirements documents, entity-relationship diagrams, process diagrams, or any other information defining the nonnative data.

2. Expand Nonnative Data Elements

After gathering information about the nonnative data, in one embodiment, the normative data element tokens (data element tokens, for example, are column names or table names) are expanded to their associated English meanings, respectively. That is, the data element tokens are expanded to their full normative data element names (Step 205 of FIG. 2). This can be referred to as “tokenizing.” FIG. 4 and Table 1 provide an illustration of tokenizing:

TABLE 1 SMT_CUS_RL_CD → Shipment Customer Role Code BIL_TER_TYP_CD → Billing Term Type Code CRR_NA → Carrier Name

In essence, expanding the data element tokens (e.g., SMT_CUS_RL_CD) facilitates understanding the data that is associated with each data element token (e.g., Shipment Customer Role Code). After expanding the data element tokens, the full normative data element names can be organized into meaningful groups. For example, each of the full normative data element names associated with billing information could be grouped together. In this example, the billing group could then be helpful in determining the scope of the billing information associated with the normative data. This is because all of the elements containing billing information would be associated with a single group. After grouping the elements, the full normative data element names can then be used to find native data elements associated with similar information as the normative data elements. For instance, the full normative data element names or words representing them can be used to query the native data to determine if any native data contains data elements associated with billing information. The query is an attempt to locate common, overlapping, or similar data between the native and normative data, e.g., searching for “like” elements. For example, if the term “manifest” were a common term in the grouping of the full normative data element names, it could be used as a search term in querying the native data. As should be recognized, the term or terms used to query the native data are not limited to group headings or the like; rather, the search term(s) may include some characteristic or attribute common to or representative of the full normative data element names. In one embodiment, this functionality can be implemented in a name matcher module 170.

Name Matcher Module

The name matcher module 170 can be used to match any native data elements associated with information that may be similar or related to the information associated with the full normative data element names (as shown in Step 210 of FIG. 2). In other words, the name matcher module 170 tries to match data elements in the normative data to like elements in the native data. By matching “like” names in the native data, the data analysis is refined. That is, the name matcher module 170 typically identifies a small subset of the native data that correlates to the various groupings of the full nonnative data element names. This matching streamlines the profiling process by decreasing the number of elements that actually need to be analyzed. The following paragraphs provide three exemplary embodiments implementing the name matcher module 170.

In one embodiment, the full nonnative data element names can be manually input into a web front-end to search the native data. For example, as shown in FIG. 5, “MANIFEST” can be an exemplary search term. In one embodiment, the results from the query would return the native data elements associated with the term manifest, as shown in FIG. 6. At this point, the results can then be exported to a program, such as Microsoft Excel (Excel) or Microsoft Access (Access), for matching the elements returned from the query to the full normative data element names. This subsequent matching can be performed, for example, manually by data analysts, with the aid of a spreadsheet program, or by an expert system.

In another embodiment a report generator can be used to generate a report containing all the native data elements. After generating the report, as shown in FIG. 7, the results can be exported to a program, such as Excel or Access. After exporting the results, the native data elements can be matched to the full normative data element names. This subsequent matching can be performed, for example, manually by data analysts, with the aid of a spreadsheet program, or by an expert system.

In yet another embodiment, a batch report can be created by using standard SQL statements to search the native metadata repository of most any relational database to return all occurrences of a requested token string. For instance, a sample batch query searching for “BILLING TERM TYPE CODE” can be executed to return an initial set of data. An exemplary batch query is shown in FIG. 8. As mentioned, this type of query is typically run on multiple databases and/or tables and will return all occurrences of a requested token string, an exemplary output of which is shown in FIG. 9. The results provide valuable information for subsequent queries, so it is preferable to retrieve more information through the query than less. The results can then be exported to a spreadsheet program that can analyze the data, such as Excel, or analyzed manually by data analysts, with the aid of a spreadsheet program, or by an expert system. After analyzing the initial set of data, the results can be imported back into the program that executed the initial query and saved as a table that can then be used as input for subsequent queries, i.e., this step uses the initial set of data from the initial query to build a table for the subsequent queries. The saved table can then be used to further refine the data by executing additional queries, such as the one shown in FIG. 10, the results of which are shown in FIG. 11. In other words, this can further refine the data so that less data needs to be analyzed. The results can then be formatted and returned to analysts for further analysis. This subsequent analysis can be performed, for example, manually by data analysts, with the aid of a spreadsheet program, or by an expert system.

3. Obtain Nonnative Data

In one embodiment, the next step in profiling data is to obtain the actual nonnative data (Step 215 of FIG. 2). In this step, all of the data can be imported, although it is entirely possible to import only some of the nonnative data. One of the challenges of importing the nonnative data is the fact that the nonnative data may be in a different format than the native data. Thus, it is often necessary to convert the nonnative data as it is imported. By converting the nonnative data into a uniform format, it allows the nonnative data to be analyzed and profiled with greater success. This conversion can be executed via a data conversion module 160.

Data Conversion Module

As shown in Step 220 of FIG. 2, the data conversion module 160 can convert data into a particular format, e.g., the format of the native data. The data conversion can be implemented by in-house programs or off-the-shelf programs such as Access or IBM's DataStage. In one embodiment, files are viewed from the perspective of being an XML file or a non-XML file. With respect to simple non-XML files, for example, Access is very flexible in that it can convert several different types of data. This flexibility makes Access a good option for converting simple non-XML files. In some embodiments, Access can also be used to convert data in an XML format. For more complex files, programs such as DataStage might be used to convert the non-XML data and/or XML data, after which the converted data can be loaded into various programs for further manipulation. As should be recognized, the programs used for data conversion are exemplary and not limiting to the various embodiments described herein.

B. Compare Nonnative Data to Information Defining Nonnative Data

In one embodiment, after the normative data is converted to a particular format, its data elements are compared to the information defining the normative data. However, for analysts to compare the actual normative data values to the information defining the normative data, the actual values must first be obtained. This can be performed in a variety of ways: 1) the values can be obtained from sources external to the normative data, e.g., metadata, or 2) the values can be obtained from the normative data itself. Obtaining the values from sources external to the normative data provides useful information, although perhaps not the most accurate. Table 2 provides potential sources for the data values and is organized from the least-current sources to the most-current source.

TABLE 2 Data Currency Information Source Least Requirements Documents Least System Documentation Medium - Most Analyst Knowledge Medium - Most DCLGENS, Copybooks, Common Tables Most Data Analysis Module

As indicated in Table 2, interrogating the data is the most accurate way to determine the contents of the data. In one embodiment, the data analysis module 150 provides this functionality, exemplary embodiments of which are discussed below.

Data Analysis Module

The data analysis module 150 typically provides the most accurate nonnative data values because it actually interrogates the data. In interrogating the data, the data analysis module 150 can perform functions such as first stage profiling, e.g., column profiling (Step 225 of FIG. 2). One of the principle functions of the data analysis module 150 is to determine the domain values, e.g., the range of values that occur in a column. There are a variety of specifically created SQL statements that implement the functionality of the data analysis module 150. As should be recognized, the statements can be written to identify all the possible unique values of the data elements within a column, table, or application. The results, e.g., the values, can then be returned to analysts for additional research. These queries 150 provide great insight to analysts reviewing the nonnative data, e.g., the results can be used to identify discrepancies between the normative data and the information defining it (e.g., metadata). Exemplary queries are shown in FIGS. 12 and 13. In the embodiment shown in FIG. 12, the data analysis module 150 executes a query that will return all values for a particular column, i.e., the query returns the value for every row in the column. As shown in FIG. 13, this query can also be executed to only return the unique values in a particular column. As mentioned, the results of the data analysis module can then be used to compare the normative data to the information defining the normative data.

1. Compare Nonnative Data Elements to Information Defining Nonnative

As mentioned, the data analysis module 150 provides analysts with information that they can use to compare to the normative data (Step 230 of FIG. 2). That is, in one embodiment, the analysts compare the output of the data analysis module 150 with the normative data to determine if there are any discrepancies between the two. This step helps analysts ensure that the information defining the normative data is accurate. The next step is to record any discrepancies.

2. Record Discrepancies between Nonnative Data and Information Defining Nonnative Data

If there are discrepancies between the nonnative data and the information defining it, analysts can record the discrepancies, as indicated in Step 235 of FIG. 2. The term “record” is used generically and includes electronically storing, writing down, documenting, or otherwise creating a record identifying the discrepancies. In one embodiment, analysts record the values of what the normative data actually contains versus what the information defining the normative data indicates. By recording discrepancies, analysts can use the information to determine the quality of the data. For instance, this step can help analysts identify: (1) code values in the data not appearing in the existing documentation; (2) data truncation; and/or (3) data transformations not defined in the existing documentation. By identifying and recording discrepancies, analysts will then be in a position to correct them.

3. Correct Discrepancies between Nonnative Data and Information Defining Nonnative Data

This step (Step 240 of FIG. 2) provides analysts with an opportunity to correct any discrepancies between the normative data and the information defining it. By reviewing the results of the data analysis module 150, analysts can then determine if any changes to the information defining the normative data need to be made. In one embodiment, for example, the corrections to the information defining the normative data might include: (1) additions and/or deletions to the domain set of codes and/or (2) updating business rules within the information defining the normative to reflect what the data reveals. At this point, analysts are typically in a position to understand the contents of the normative data to better evaluate possibilities for integrating the normative data with the native data.

C. Compare Nonnative Data Elements to Information Defining Native Data 1. Gather Information Defining Native Data

In one embodiment, the next step (Step 245 of FIG. 2) in profiling the data is to gather, import, or receive (hereinafter the terms are used interchangeably) information defining the native data. As mentioned previously, the information received can include data dictionaries, metadata (tool-generated or home-grown), copybooks, table schemas, data models, common tables and contents, requirements documents, entity-relationship diagrams, process diagrams, or any other information defining the nonnative data. Typically only information defining elements that are similar to or like the full nonnative data element names is received. This is because the similar elements are considered the “best candidates” for integration. In one embodiment, to determine the best candidates for integration and information about them, a data element matcher module 140 can be used. In this embodiment, the data element matcher module 140 uses the output from the name matcher module 170, which may have been further refined by analysts, as input.

Data Element Matcher Module

The data element matcher module 140 performs what is typically known as second and third stage profiling (Step 250 of FIG. 2). The data element matcher module 140 can receive a list of native candidate elements and return information that provides a context of how the data elements are used in the native data. For example, the results can show where a specific element is being used, how the data is being used in various applications, and any current and/or previous usages of the data. This enables analysts to further understand the scope of the information contained in the elements. The information can then be used to compare the uses and attributes of the native candidate elements to the nonnative data.

To do so, in one embodiment, the data element matcher module 140 generates an “Approved Elements Report” from a list of candidate elements. The list of candidate elements is typically received from the output/data of the name matcher module 170 that may have also been refined by analysts or received from other steps. An exemplary list of candidate elements is shown in FIG. 14. In one embodiment, this input is used to generate an Approved Elements Report. The Approved Elements Report typically only contains information of approved or active native data elements. An exemplary Approved Elements Report is shown in FIG. 15. The report indicates: (1) applications where elements are used; (2) element names; (3) tables in each application where elements are used; (4) acronyms of the applications; (5) business names of each element; (6) data types; and (7) lengths of the element. This information is extremely valuable to analysts to help identify other native applications where the data is being used and to evaluate how the data is being used. This information can then be compared to the use and attributes of the nonnative data.

In one embodiment, the data element matcher module 140 can also generate an “Obsolete to Approved Association Report.” The Obsolete to Approved Association Report contains similar information as the Approved Elements Report, but may also contain information of data elements that are no longer recognized as active or approved but that are still being used by some applications. The Obsolete to Approved Association Report can also display the relationships between the obsolete elements and the active or approved elements. To generate this report, the data element matcher module 140 also needs a list of “candidate elements.” As mentioned, the input of candidate elements is typically received from output/data of the name matcher module 170 that may have also been refined by analysts or received from other steps. An exemplary list of candidate elements is shown in FIG. 14. In one embodiment, this input is used to generate the Obsolete to Approved Association Report, an exemplary report is shown in FIG. 16. The report indicates the: (1) applications where elements are used; (2) tables in each application where elements are used; (3) acronyms of the applications; (4) obsolete element names; (5) active element names; (6) business names of each element; (7) data types; and (8) lengths of the elements. This information also provides a context of how the data elements are being used, which can be compared to the use and attributes of the nonnative data. As mentioned, by generating this additional report, an additional level of finding potential matches for integration can be achieved. Once this information is available, the list of native candidate elements can be created and the information defining these native data elements can be compared to the nonnative data elements.

2. Compare Nonnative Data Elements to Information Defining Native Data

The data element matcher module 170 provides analysts with a list of elements and information about how and where the elements are used. Analysts can compare the information defining the native data elements from the data element matcher module 140 to the normative data elements, as indicated in Step 255 of FIG. 2. The goals of this step are to: (1) identify the differences between the information defining the native data and the normative data elements and (2) finalize the list of native candidate elements for integration with the nonnative data. By comparing the information to the normative data, analysts can determine if there are any discrepancies between the normative data and the information defining the native data.

3. Record Discrepancies between Nonnative Data and Information Defining Native Data

In one embodiment, the next step (Step 260 of FIG. 2) is to record any discrepancies between the nonnative data and the information defining the native data. As previously indicated, the term “record” is used generically and includes electronically storing, writing down, documenting, or otherwise creating a record identifying the discrepancies. By recording the discrepancies between the nonnative data and the information defining the native data, analysts will then be in a position to correct the discrepancies between them.

4. Correct Discrepancies in Information Defining Native Data

Identifying the discrepancies can assist analysts in making decisions concerning how to modify the information defining the native data, such as (1) revising the information defining the native data by, for example, expanding the information to include the nonnative data meanings; (2) extending the existing domain values to include examples of normative data values; and/or (3) establishing normative data transformation rules (Step 265 of FIG. 2). At this point, the normative data and data can be integrated, rules can be established for integration, and/or additional profiling can be performed.

D. Additional Data Profiling Analysis

In one embodiment, additional data profiling analysis can be performed on the normative data, although in some cases this step is unnecessary. If additional analysis is performed, it is typically done to provide a level of data analysis beyond that of profiling the data contained in a column, table, and application, e.g., it may provide data frequency information of specific elements. The data frequency information can be very useful, for example, in evaluating data trends, such as the overuse of null or default values.

1. Determine Frequencies of Nonnative Data Values

In one embodiment, analysts use additional profiling tools to perform frequency data analysis on the nonnative data. Understanding the number of times a specific value occurs in a set of data can provide useful information to analysts making integration decisions (Step 270 of FIG. 2). For instance, a high frequency of null or default values may indicate that the application is not enforcing its population or default values. Determining the frequency of various values can be performed by data integration tools, such as the data frequency module 130.

Data Frequency Module

To determine various frequencies, the data frequency module 130 typically receives input from analysts, such as nonnative element names, values, tables, and/or columns (Step 275 of FIG. 2). The data frequency can then profile the data (1) within column; (2) within table; (3) and/or across all tables in the application. These levels build on each other with regard to identifying all of the possible places a specific element and its contents can be found as well as how frequently the values appear within a column, table, or application. An exemplary output is shown in FIG. 17. In FIG. 17, the first column shows the unique values, the second column shows the number of times the values occur in the column, and the third column shows the frequency percentage of the values in the column. The results from the data frequency module 130 can then be saved or otherwise recorded for use by analysts.

2. Identify Frequency of Values

In one embodiment, once the data frequency module 130 generates output, analysts can review the information (Step 280 of FIG. 2). For instance, analysts can determine if the frequency of a particular value of an element is higher or lower than expected. This step might require that the analysts have additional knowledge about the data, for example, knowledge as to why a particular value might be present at an increased frequency (e.g., a common customer type, country code, or commodity). There may, in fact, be valid business reasons for a high or low frequency of a given value. Thus, in analyzing the data, analysts often have questions that require additional research or consultation with others.

3. Determine if Additional Analysis is Needed/Ask Business Questions

As previously mentioned, analyzing the data frequency can lead to additional questions and/or research (Step 285 of FIG. 2). For example, the data frequency may give rise to questions such as (1) how the data is populated at the point of capture or (2) what type of editing should be done to prevent a high frequency of default or null values. Some of the questions might not be answerable by the analysts performing the data profiling. Thus, some of the questions or issues raised can be given to others, such as business units, to answer and/or solve. At this point, the nonnative data and data can be integrated and/or rules can be established for integration.

E. Rules for Integrating Native Data and Nonnative Data

After the data is analyzed, the profiling can be considered complete. However, in one embodiment, there are additional steps considered as being part of the integration process. The additional steps aid in the actual integration of the native and nonnative data.

1. Establish Rules for Integrating Native Data and Nonnative Data

In one embodiment, establishing transformation rules is an important part of the data integration process (Step 290 of FIG. 2). For instance, transformation rules can be used for: (1) code value translation; (2) truncation or elongation of fields; (3) numeric to alphabetic conversion and vice versa; and/or (4) region and/or organization translation. The transformation rules can be created in concert with business knowledgeable resources associated with both the native and nonnative data to ensure proper translation and integration.

2. Record Rules for Integrating Native Data and Nonnative Data

As indicated, one of the final steps of the process is to record the established transformation rules (Step 295 of FIG. 2). That is, the transformation rules established in the previous step, e.g., Step 290, are recorded. As mentioned, the term “record” is used generically and includes electronically storing, writing down, documenting, or otherwise creating a record of the established rules. In one embodiment, analysts store the transformation rules electronically such that they can be used by a population tool, e.g., an ETL (extract, transform, and load) tool, to integrate the data. The established transformation rules can also be recorded with the information recorded in Steps 235 and 260, i.e., with the information defining the native data and/or the information defining the nonnative data. At this point, the native data and nonnative data can be integrated.

In the preceding specification, various embodiments have been described. It will, however, be evident that various modifications and changes may be made thereunto without departing from the broader spirit and scope of the embodiments as set forth in the claims that follow. In fact, many of the embodiments are described as steps; however, the order of the steps described is not necessarily the order in which the steps are performed. That is, the order of the steps may vary and still be within the scope of the various embodiments of the present invention. Moreover, some of the steps can be omitted and additional steps can be added and still be within the scope of the present invention. Thus, the specification and drawings are to be regarded in an illustrative rather than in a restrictive sense. 

1. A method for integrating nonnative data with native data comprising: receiving, via a computing device, information defining nonnative data; expanding normative data element tokens to their respective full normative data element names; searching native data, via a computing device, to determine if information associated with any of the respective native data elements and information associated with any of the respective full normative data element names are similar; importing the normative data via a computing device; identifying values of the normative data via a computing device; comparing the normative data to the information defining the normative data to determine if there are any discrepancies between the information defining the normative data and the normative data; in response to a determination that there are discrepancies between the nonnative data and the information defining the normative data, recording the discrepancies and determining if the information defining the normative data needs to be modified; in response to a determination that the information defining the normative data needs to be modified, modifying the information defining the normative data; in response to a search determining that at least one native data element and one full normative data element name are associated with a similar type of information, receiving information defining the similar native data elements; comparing the normative data to the information defining the similar native data elements to determine if there are discrepancies; in response to a determination that there are discrepancies between the nonnative data and the information defining the similar native data elements, recording the discrepancies and determining if the information defining the native data needs to be modified; and in response to a determination that the information defining the native data needs to be modified, modifying the information defining the similar native data elements.
 2. The method of claim 1 further comprising: combining the nonnative data with the native data via a computing device.
 3. The method of claim 1, wherein importing the nonnative data further comprises converting the nonnative data to a native format.
 4. The method of claim 3, wherein the nonnative data is an XML format.
 5. The method of claim 1 further comprising: determining the frequency of values in at least a column or table in the nonnative data via a computing device.
 6. The method of claim 1 further comprising: establishing rules to combine the nonnative data with the native data.
 7. The method of claim 6 further comprising: recording the rules used in combining the nonnative data with the native data.
 8. The method of claim 6 further comprising: combining the nonnative data with the native data in accordance with the established rules via a computing device.
 9. The method of claim 1, wherein comparing the nonnative data to the information defining the nonnative data further comprises obtaining the values associated with the respective data element tokens via a computing device.
 10. A system for integrating nonnative data with native data comprising: a processor configured to: receive information about native data and nonnative data, including full nonnative data element names and native data elements; search native data to determine if information associated with any of the respective native data elements and information associated with any of the respective full normative data element names are similar; import the normative data; identify values of the nonnative data; record any discrepancies between the information defining the normative data and the normative data; receive information defining the similar native data elements; and record any discrepancies between the normative data to the information defining the similar native data elements.
 11. The system of claim 10, wherein the processor is further configured to: combine the normative data with the native data.
 12. The system of claim 10, wherein to import the normative data, the processor is further configured to convert the normative data to a native format.
 13. The system of claim 12, wherein the normative data is an XML format.
 14. The system of claim 10, wherein the processor is further configured to: determine the frequency of values in at least a column or table in the normative data.
 15. The system of claim 10, wherein the processor is further configured to: establish rules to combine the normative data with the native data.
 16. The system of claim 15, wherein the processor is further configured to: record the rules used in combining the normative data with the native data.
 17. The system of claim 15, wherein the processor is further configured to: combine the normative data with the native data in accordance with the established rules.
 18. The system of claim 10, wherein to compare the nonnative data to the information defining the nonnative data, the processor is further configured to obtain the values associated with the respective data element tokens. 